Checklist

• npm test passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

Description of change

Similar to this PR: #30

1. Added displayErrors option

I added a displayErrors option, (like php display_errors). Because we can not say if env !== 'local' or env !== 'unittest' then env = 'prod', there are may test/uat...environments that we still need to show error stacks. I added this option so that we don't need to use env variable to see display errors or not. That's user behaviors. if they need to display errors in different env, then they can easily handle it in config files, like:

{
  displayErrors: process.env.NODE_ENV !== 'production'
}

or

{
  displayErrors (app) => app.env !== 'prod'
}

2. Added displaySections option

For some sections in error page, they are highly sensitive, like the appInfo section, or cookie section. Normally it contains the server side database password or user sensitive information. If we want to display errors in test/uat environment. then we should not to display those information to everybody. So I added this option. so that user can customize what section they want to show in the error pages